PR Summary

Fixes #1206
When PowerShell starts at a directory and a script has an expression like the dot operator to a relative path that exists, Get-Command returns an object and makes it correct the path to the file name in the new UseCorrectCasing formatting rule (this rule is turned off by default in the vs code editor). We do not want to change paths at all (there could even be path casing issues if someone develops on Windows for example), therefore the exclusion applies. It was hard to write a test case for this but the same bug also occurs when using a UNC file path and this was chosen to be the test case for the written regression test.

In general we also found more edge cases of application paths being corrected as well and takie this logic out as well due to the time pressure of shipping 1.18.1 It seemed something easy for free at first but that was actually not the intent of the rule and it seems it is anon-trivial feature that someone might want to add later but not now.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
• Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.